\section*{SRS Documents}
The SharingBooks team does address a well-defined problem. The problem stated is
that there is a need to buy, sell, trade, and loan books all in one single
application. The competitors all have parts, but none of them have the complete
package. The audience is anyone who wishes to share books or to borrow books,
but it seems that they are focused on the textbook aspect which would mean the
audience would be focused mainly on college students.

The requirements state there are many features that would be implemented.
However, the use cases seemed to only focus on a couple, leaving the usage of
the other features up to the reader's imagination.  Even then, we would have
considered the first use case, `Search/Find Books', to be a subset of the
`Trade, Loan, or Sell Book' use case. We were disappointed not to see how a user
might use some of the many other features that were mentioned. For example, it
would be nice to see how a user would barter with another user, or how the
rating system would work. These missing use cases seem to detract from a good
understanding of the product as a whole.

The major features that they did implement are pretty useful.  However, they
seem to have a very modal system where one can only use a single feature at a
time, forcing the user to completely exit one feature to use another. Besides
that, the implemented ones seem somewhat useful such as searching for books and
adding it into your library. As explained above, they did fail to display the
use of some additional features.

It is mentioned very briefly that documentation will be hosted on the site in
the form of a Frequently Asked Questions page, a Help page, and an About
page. These are very common for this type of application and it makes sense to
have those. If it is possible, an integrated tutorial for a first-time user
might be helpful as well. They could perhaps implement this as a series of tip
boxes that pop up every time they enter a new section of the application.

In terms of time constraints, our team thinks that they have included more
options than they have time for. We think they should focus on the
finding/trading, loaning, and selling aspects rather than on less important
features like specialized interest groups that users can join who like a certain
genre of a book.

The UI seems intuitive for the stage we are in; however there is no mention of
how it will look integrated into Facebook. It isn't required, but an idea of
what it will look like in conjunction with the site would be nice. There was
also some confusion as to how users would determine the shipping method. Would
it be part of the bartering system, within the Facebook messaging system, or
some other way?

All in all, the SRS documents seem well put together and planned out. From the
look of the documents, the group seems to be organized, to have a good
understanding of their system, and to be well prepared for the rest of
their development stages.

\begin{comment}
Questions:
 - Is the project addressing a well-defined problem?
 - Does it provide value in ways that not met by the alternatives?
 - Is there a well-defined audience?
 - Are the requirements clear?
 - Are useful features missing?
   - How useful are their presented major features?
 - Will they provide useful documentation?
 - How important are the presented use cases? (Did they miss any?)
 - Does this project fit under the time constraints of 403?
\end{comment}